Tree

There is a problem

1000 entries with tree-preservation-order field must match the reference field in the tree preservation order

1393

reference: 615-tree-1
name: 1393
tree-preservation-order: undefined
615-tpo-1
uprn
address-text
point: POINT (-1.023472 50.881068)
geometry: MULTIPOLYGON (((-1.023443 50.881065,-1.023444 50.881071,-1.023448 50.881076,-1.023463 50.881083,-1.023471 50.881084,-1.023480 50.881083,-1.023488 50.881080,-1.023499 50.881071,-1.023500 50.881066,-1.023499 50.881060,-1.023495 50.881055,-1.023489 50.881051,-1.023472 50.881048,-1.023463 50.881048,-1.023455 50.881051,-1.023449 50.881055,-1.023443 50.881065)))
notes
felled-date
entry-date: 2026-08-06
start-date
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The tree guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that affects this tree.

Example: TPO1

This diagram shows the relationship between the tree preservation order dataset and the tree dataset. The reference value from your tree preservation order dataset needs to match the tree-preservation-order value in your tree dataset.

How to improve East Hampshire District Council’s data

Fix the errors indicated
Use the check service to make sure the data meets the standard
Publish the updated data on the endpoint URL